home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group97a.txt
/
000084_icon-group-sender _Fri Mar 14 18:13:45 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
1KB
Received: by cheltenham.cs.arizona.edu; Sat, 15 Mar 1997 05:54:12 MST
Date: Fri, 14 Mar 97 18:13:45 GMT
Message-Id: <16791.9703141813@subnode.aiai.ed.ac.uk>
From: Jeff Dalton <jeff@aiai.ed.ac.uk>
Subject: Re: Recursive directory traversal in Icon
To: Jan Galkowski <jan@digicomp.com>, icon-group@cs.arizona.edu
In-Reply-To: Jan Galkowski's message of Thu, 13 Mar 1997 14:53:19 -0500
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Content-Length: 857
In-Reply-To: Jan Galkowski's message of Thu, 13 Mar 1997 14:53:19 -0500
> To only slightly exaggerate, there's nothing in any "module
> system" which can't be modelled in a proper implementation of the lambda
> calculus, e.g., in SCHEME. So, one possible explanation is that a
> "module system" is in some important sense excess baggage.
An important reason why Scheme does not have modules is that people
are not able to agree on what the module system should be. Some
particular Scheme implementations do have modules, though.
Some Scheme module systems can be implemented entirely in Scheme,
but they would typically use Scheme's macros was well as the lambda
calculus parts of the language.
To me, at least, Scheme's lack of modules is a serious limitation
and one of the main reasons I usually use Common Lisp rather than
Scheme.
-- jeff